Device migration

ABSTRACT

Personalization data such as settings and/or state is migrated across devices including mobile phones. Device personalizations are pushed to a cloud service or other mechanism for backup and subsequent transmission to other devices. The personalization data can later be employed to configure one or more other devices in the same manner as a first device.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 14/263,317 entitled “Device Migration”, filed Apr. 28, 2014,which is a continuation of U.S. patent application Ser. No. 11/864,636entitled “Device Migration”, filed Sep. 28, 2007 (issued as U.S. Pat.No. 8,744,423 on Jun. 3, 2014), the contents of which are herebyincorporated by reference in their entirety.

BACKGROUND

Computers and other processor-based devices are pervasive in today'ssociety. Although originally the sole domain of well-funded companiesand research institutions, technology advancements and cost reductionsover time have enabled computers and other electronic devices to becomecommonplace in the lives of most everyone. Continued technologicaladvancements over time have led to a dramatic decrease in both size andcost of electronic components. As a result, the popularity of bulkydesktop-style computers is giving way to smaller mobile devices such asmobile phones, personal digital assistance, and/or media players.

The most popular of the mobile devices are communication devices ingeneral and more particularly mobile or cellular telephones. Not toolong ago mobile communication devices were luxury items affordable onlyto those with substantial means. Moreover, these devices were ofsignificant size rendering them inconvenient for extended portableemployment. In contrast, most current mobile communication devices canbe carried easily in a user's pocket or handbag. Furthermore,conventional devices include added functionality such as gameapplications, web access, address books, image capture/display videocapture/display, and text messaging.

Additionally, mobile communication device development and refinementcontinues to occur at an expeditious pace. Advancements in mobilecommunication devices are largely a function of consumer demand. Inorder to fulfill consumer needs, the industry provides a plurality ofdevices (e.g., models of devices having various applications, andfeatures). Smaller devices, game applications, web access, storagecapacity, display size, ergonomics, phonebook storage, longer batterylife, are a few examples that encourage the mobile communication deviceindustry to improve upon existing technology.

Mobile devices are increasing in technological ability affording aplurality of functionality within a limited device-space. Mobile devicescan include cell phones, personal digital assistance, pagers, messengerdevices, handhelds or palmtops, and smart phones, among others. Althougheach device provides a specific function, devices have been developingto allow overlapping functionality in order to appeal to consumer needs.For example, cell phones can provide cellular service, phonebooks,calendars, games, voicemail, paging, web browsing, video capture, imagecapture, voice memos, and voice recognition.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the claimed subject matter. Thissummary is not an extensive overview. It is not intended to identifykey/critical elements or to delineate the scope of the claimed subjectmatter. Its sole purpose is to present some concepts in a simplifiedform as a prelude to the more detailed description that is presentedlater.

Briefly described, the subject disclosure pertains to device migration.More specifically, device personalizations such as installedapplications, content, settings, state, and the like can be storedutilizing a cloud service or other transport mechanisms to facilitatedynamic access and/or transfer of such information to other devices.Among other things, this provides a type of backup to ensure thatpersonalizations are not lost and relieves users from the time-consumingand frustrating process associated with reinstallation and/orcustomization. Additionally or alternatively, device migration canfacilitate utilization of multiple devices with substantially the samelevel of details and settings.

In accordance with one aspect of the disclosure, personalizations can bepartitioned as a function of multiple identities and/or personas. Forexample, a device can be dynamically configured for one or more businessand/or personal modes automatically, semi-automatically or in responseto an explicit instruction.

According to another aspect, personalization data can be, standardized,normalized, and/or translated to facilitate migration acrossheterogeneous devices. In other words, mechanisms are provided forabstracting, normalizing, or translating personalization data to ensureit is usable, renderable, or otherwise appropriate for different devicesand/or device classes.

In accordance with another aspect of the disclosure, personalizationdata can be streamed to a device as a function of device capabilityand/or network connectivity. Various caching mechanisms such as eagerand deferred loading are provide to facilitate operation. For instance,all or a portion of personalization data can be pre-fetched and cachedor persisted on device. Otherwise, such data can be lazy loaded on an asneeded basis or a hybrid of the two.

In accordance with yet another aspect, personalization data can bemigrated to secondary devices. Further, communications andpersonalizations can be split across multiple devices to provide aricher environment. The split can be a function of location among otherthings and can dynamically update in response to changing position.

To the accomplishment of the foregoing and related ends, certainillustrative aspects of the claimed subject matter are described hereinin connection with the following description and the annexed drawings.These aspects are indicative of various ways in which the subject mattermay be practiced, all of which are intended to be within the scope ofthe claimed subject matter. Other advantages and novel features maybecome apparent from the following detailed description when consideredin conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of data migration system in accordance with anaspect of the disclosed subject matter.

FIG. 2 is a block diagram of a data migration system that facilitatesnormalization and/or translation of data in accordance with an aspect ofthe disclosed subject matter.

FIG. 3 is a block diagram of a device migration system in accordancewith an aspect of the disclosed subject matter.

FIG. 4 is a block diagram of a data migration system that facilitatescaching of data in accordance with an aspect of the disclosed subjectmatter.

FIG. 5 is a block diagram of a system that alters data migration basedon device availability in accordance with an aspect of the disclosedsubject matter.

FIG. 6 is a block diagram of a migration system that distributes dataacross multiple devices in accordance with an aspect of the disclosedsubject matter.

FIG. 7 is a flow chart diagram of a method of data migration accordingto an aspect of the claimed subject matter.

FIG. 8 is a flow chart diagram of a method of device configuration inaccordance with an aspect of the claimed subject matter.

FIG. 9 is a flow chart diagram of device configuration according to anaspect of the disclosed subject matter.

FIG. 10 is a flow chart diagram of a communication processing methodutilizing device migration in accordance with an aspect of the disclosedsubject matter.

FIG. 11 is a flow chart diagram of a multiple device migration method inaccordance with an aspect of the disclosed subject matter.

FIG. 12 is a schematic block diagram illustrating a suitable operatingenvironment for aspects of the subject disclosure.

FIG. 13 is a schematic block diagram of a sample-computing environment.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Systems and methods described hereinafter relate to data migrationbetween devices in general. More specifically, personalization data orinformation is migrated from one device to another. In one embodiment,such information can be backed-up utilizing a remote service andsubsequently employed to configure other devices to be substantiallyidentical to another device for example with respect to contacts,settings, preferences, among other things. According to one aspect,dynamic caching and/or synchronization can occur as a function of devicecapability and/or availability. Further, where unavailable, data can beredirected to another device. Still further yet, such information can bedistributed across multiple devices.

Various aspects of the subject disclosure are now described withreference to the annexed drawings, wherein like numerals refer to likeor corresponding elements throughout. It should be understood, however,that the drawings and detailed description relating thereto are notintended to limit the claimed subject matter to the particular formdisclosed. Rather, the intention is to cover all modifications,equivalents, and alternatives falling within the spirit and scope of theclaimed subject matter.

Referring initially to FIG. 1, a data migration system is illustrated inaccordance with the claimed subject matter. The system includes a cloudservice 110 that provides remote network accessible functionality. Thisspecific cloud service 110 includes a migration component 112 as well asone or more data stores 114. Accordingly, it can alternatively bereferred to as a migration cloud service. The cloud service 110 isaccessible by a plurality of mobile devices 120. As shown, the cloudservice 110 is accessed by device “1” and device “N+1,” where “N” is aninteger greater than or equal to one. In one embodiment, the devices 120can correspond to mobile communication devices including mobile orcellular telephones, or the like; however, the claimed subject matter isnot limited thereto.

The devices 120 are communicatively coupled to the cloud service 110 toenable interaction or receipt and transmission of data. Moreparticularly, personalizations or personalization data is exchangedincluding, among other things, installed applications, content (e.g.,music, video, pictures . . . ), settings, state, and the like. The type,kind, and extent of data can be a function of device-supportedfunctionality. For example, where the devices 120 correspond to mobilephones the data can include contacts, ring tones, settings, preferences,and/or rules.

Each device 120 can include an interface component 122 to facilitateinteraction. The interface component 122 can communicate directly orindirectly with the migration component 112 of the cloud service 110. Inone instance, the interface component 122 can upload personalizationdata such as settings and/or state information 124 to the cloud service110, which can store the uploaded data to the one or more data stores114. This can be done upon explicit command or automatically as afunction of change, for instance, to keep the data up to date orsynchronize the data. Alternatively, the interface component 120 canfacilitate receipt and/or retrieval of previously uploadedpersonalization data including setting and/or state information from thecloud service 110.

The migration component 112 can manage acquisition and provisioning ofdata to and/or from multiple devices 120. This component or anassociated interface (not shown) can be available to receive data from adevice 120 and persist the data to at least one data store 114.Additionally, the migration component 112 can respond to a request fordata from a device 120 by retrieving the appropriate data from at leastone data store 114 and providing or otherwise making the data availableto the device 120.

By way of example and not limitation, mobile phone data can be migratedbetween multiple phones. Personalization data can be uploaded from afirst or primary mobile phone to the cloud service 110. Later this datacan be downloaded to a second phone for use where desired. Additionallyand as will be described further infra, acquired data can be utilized toconfigure the phone. In this manner, phones can be configured to besubstantially identical to others. This can be beneficial in manysituations. For instance, upon purchase of a new phone allcustomizations on an old phone including pictures, ring tones andapplications can be effected on the new phone. Additionally, a purchasedor rented phone utilized in connection with world travel can be setupautomatically to appear substantially the same as a primary phone.Further, individuals may have multiple phones (e.g., work, home,personal . . . ) in which case changes on one can be propagated toothers affording the same level of detail and settings.

While migration functionality can be effectuated utilizing a cloud asprovided herein, it is to be noted that the claimed subject matter isnot limited thereto. Aspects of data migration described above as wellas below can be transport agnostic. In other words, migration of state,settings, and/or the like can be embodied with respect to othertransport mechanisms besides a network-based service. By way of exampleand not limitation, a user can plug a flash memory stick into a devicesuch as a phone extract the settings and move them to a new phone.

FIG. 2 depicts data migration system 200 in accordance with an aspect ofthe claimed subject matter. Similar to FIG. 1, the system 200 can be acloud service and include the migration component 112 and one or moredata stores 114, as previously described. However, data migration neednot be limited to the same or substantially the same devices.Accordingly, the system 200 can include one or more of normalizationcomponent 210 and translation component 220. The normalization component210 can normalize or standardize persisted data or data to be persistedto one or more data stores 114. Data from various device manufacturerscan be in different or proprietary in nature. The normalizationcomponent 210 can map this data to a standard format for storage andsubsequent use.

The translation component 220 can translate data from a first format toa second format. In one instance, the translation component 220 canconvert a standardized format to a proprietary format. However, thetranslation component 220 can also convert between source and targetproprietary formats. Furthermore, translation can be between settings ofdissimilar types on different devices or device classes. For example,one device can be a touch screen phone with settings and/or statesassociated with the fact that it is touch screen. These settings and/orstates need not be pushed down to a non-touch screen phone since theyare irrelevant. In other words, settings content can be abstracted toensure it is usable, renderable, or appropriate on different classes ofdevices.

Turning attention to FIG. 3, a device migration system 300 isillustrated in accordance with an aspect of the claimed subject matter.Similar to system 100 of FIG. 1, system 300 includes the interfacecomponent 122 to facilitate interaction with a migration cloud service.More specifically, the interface component 122 can provision data to oracquire data from a cloud migration service. In one instance, data cansimply be downloaded and saved on a device (e.g., music, picture . . .). Additionally or alternatively, the device can utilized such data tofurther customize the device. In accordance with one aspect, settingsand/or state information can be acquired by the device. Configurationcomponent 310 can employ such information to configure a device tofunction substantially similar to another device. For example, contactscan be populated, ring tones fixed, wallpaper set, and applicationsloaded, among other things.

The system 300 also includes an identity component 320 to enable furthercustomization. Individuals are often associated with multiple identitiesor personas. For instance, users often have different business andpersonal identities. The identity component 320 enables a user to set anidentity and cause a device to be configured in accordance with thatidentity. In effect, this can correspond to requesting and/or acquiringidentity or mode specific information via interface component 122 from adata migration service, which can partition data in this way. By way ofexample, user mobile device such as a mobile phone can be configured fora business mode or a personal mode. Here, a different set of contacts,rules, policies, ring tones, songs, favorites, settings, among otherthings can be loaded as a function of the mode. Hence, the device candynamically configure settings, contacts and the like in the evenings orweekends for use in a non-business more personal manner and vice versafor working hours.

Devices can be programmed to change modes in response to an explicitcommand and/or semi-automatically. For instance, a user can explicitlyselect a particular mode or identity for which a device is to beconfigured. Alternatively, a user can set up rules or preferences todrive a more automatic transition between modes. For example, a mobilephone can be designated for business use during the hours of 9 a.m. and5 p.m. Monday through Friday and otherwise it is configured for personaluse.

Furthermore, modes can be altered automatically as a function of contextinformation received or retrieved by the context component 330. In thiscase, context information such as geographical location can be utilizedto infer a mode or identity and automatically and dynamically configurea mobile device. Additional contextual information can include proximityto other individuals, among other things. For example, a devicecomponent can communicate with other devices within a predefined areavia a near field communication (NFC) technology to identify their ownersand/or modes. This information alone or in combination with othercontext information such as geographical location, time and date can beutilized to infer a user identity and/or device mode and initiateconfiguration in accordance with the identity and/or mode. Variousmachine-learning mechanisms can also be utilized to ultimately improvethe accuracy of inference over time.

Referring to FIG. 4, a cloud data migration system 400 is depicted inaccordance with an aspect of the claimed subject matter. As similarlyshown and described with respect to FIGS. 1 and 2, the system 400includes the migration component 112 and one or more data stores 114 toenable migration of personalization data between and/or amongst devices.Further provided is cache component 410 communicatively coupled to themigration component 112. While the migration component 112 can simplyprovide all personalization data or the like in one transaction, theprocess can be more continuous and interactive via employment of thecache component 410. The cache component 410 can control or throttledata afforded to devices as a function of one or more variables such asdevice capability and/or network connectivity, among other things.

Devices often include differing processing capabilities. Accordingly, adevice may not be able to be configured and/or locally store all dataassociated with another device. For example, one device can be apowerful smart phone and the other a thin client phone. Alternatively,for security and other reasons it might not be desirable to house allpersonalization information on a device. The cache component 410resolves this dilemma by providing the phone with as much data as it canhandle in an efficient and/or secure manner and on an as needed basis.

More specifically, the cache component 410 can enable eager and/ordeferred loading of data at various levels of granularity. For instance,the cache component 410 can enable eager loading or pre-fetching of datawhere it can be determined that it will likely be needed in the future.Additionally or alternatively, the cache component 410 can enabledeferred or lazy loading of data, wherein the data is only loaded whenrequested. By way of example, where a contacts list is substantiallylarge and/or available storage space is relatively small the cachecomponent 410 can ensure that the most popular or most recently usedcontacts are pre-fetched and loaded on the device, and other contactinformation can be loaded lazily upon request. Similarly, data can becached as a function of network availability or predicted availability.For instance, if a device senses that it is approaching an area whereconnectivity may be lost, it can pre-fetch more content and persistedsuch information to the device.

FIG. 5 depicts a cloud migration system 500 in accordance with an aspectof the claimed subject matter. As previously described, system 500includes a migration component 112 and one or more data stores 114.Furthermore, the system 500 includes a monitor component 510. Themonitor component 510 monitors the device availability and initiates orredirects migration to alternate devices in the event the first orprimary device is unavailable. For example, the migration system 500 canlose contact with a mobile communication device where it is out ofservice range or its battery dies, among other things. Where the monitorcomponent 510 determines that a device is unavailable, for instanceafter a predefined period of unresponsiveness, and a communication isdirected to the device such as a call, data can be routed to anotherdevice in accordance with a rule, preference or other mechanism.

Consider the situation where a user's mobile phone battery dies and anincoming call is received. Not only can the call be transferred orredirected to another phone such as that of a detected friend nearby(e.g., using NFC), but all or a portion of personalization data can bealso be transferred. In other words, the call and all or a portion ofphone settings can be moved to another device. In this case, the friendcan notify the user that they have a call that has been transferred totheir phone and the user can answer the call on the friend's phone,wherein the phone is loaded with the same of similar personalizationdata. Accordingly, the user can also subsequently look up their contactsutilizing the friend's phone to notify others that his/her battery hasdied and to call a different number or leave a message.

Referring to FIG. 6, a migration division system 600 is illustrated inaccordance with an aspect of the claimed subject matter. The system 600includes a migration component 112 and one or more data stores 114 aspreviously described. In brief, the migration component 112 accepts anddistributes personalization data housed in data store(s) 114 such asinstalled applications, content (e.g., music, video, pictures . . . ),settings, and/or state, amongst others to devices. Up to this point,discussion has been focused on transferring personalization data tosingle devices. The claimed subject matter is not so limited.

System 600 also includes a device detection component 610 that canidentify secondary devices and a split component 620 for dividingcommunications and personalized data across multiple devicesconcurrently. The device detection component 610 can identify secondarydevices as a function of location and/or near field communicationtechnologies, among other means. Upon identification of such a device,migration component 610 can migrate or move a portion of communicationand personalization settings to the secondary device. For example, thevideo portion of a video phone call and associated personalizationsettings can be migrated to a proximate television to enable the call tobe carried out in a richer environment. Furthermore, as a user movesvideo can continue to be migrated to the closest television.Alternatively, a mobile video call can be migrated to a house phone andplasma television and further migrate as the user changes locations.Migrated data, applications, and the like can adapt to the capabilitiesof the new device (e.g., screen real estate, processing capabilities,memory . . . ).

The aforementioned systems, architectures and the like have beendescribed with respect to interaction between several components. Itshould be appreciated that such systems and components can include thosecomponents or sub-components specified therein, some of the specifiedcomponents or sub-components, and/or additional components.Sub-components could also be implemented as components communicativelycoupled to other components rather than included within parentcomponents. Further yet, one or more components and/or sub-componentsmay be combined into a single component to provide aggregatefunctionality. Communication between systems, components and/orsub-components can be accomplished in accordance with either a pushand/or pull model. The components may also interact with one or moreother components not specifically described herein for the sake ofbrevity, but known by those of skill in the art.

Furthermore, as will be appreciated, various portions of the disclosedsystems and methods can include or consist of artificial intelligence,machine learning, or knowledge or rule based components, sub-components,processes, means, methodologies, or mechanisms (e.g., support vectormachines, neural networks, expert systems, Bayesian belief networks,fuzzy logic, data fusion engines, classifiers . . . ). Such components,inter alia, can automate certain mechanisms or processes performedthereby to make portions of the systems and methods more adaptive aswell as efficient and intelligent. By way of example and not limitation,the identity component 320 can employ such mechanisms to facilitateinferring an identity, persona, or mode.

In view of the exemplary systems described supra, methodologies that maybe implemented in accordance with the disclosed subject matter will bebetter appreciated with reference to the flow charts of FIGS. 7-11.While for purposes of simplicity of explanation, the methodologies areshown and described as a series of blocks, it is to be understood andappreciated that the claimed subject matter is not limited by the orderof the blocks, as some blocks may occur in different orders and/orconcurrently with other blocks from what is depicted and describedherein. Moreover, not all illustrated blocks may be required toimplement the methodologies described hereinafter.

Referring to FIG. 7, a method 700 of data migration is illustrated inaccordance with an aspect of the claimed subject matter. At referencenumeral 710, personalization data is provided to a cloud service. Thepersonalization data can include a set of data associated withpersonalizing or customizing a device for use by a particular user. Thisset of data can include installed applications, content (e.g., music,video, pictures . . . ), settings, and/or state, among other things. Atreference 720, this personalization data is provisioned to anotherdevice. In this manner, a second device (e.g., new, rented, borrowed,additional) can be instantiated to appear and/or operate in the same ornearly the same way as a first device. By way of example and notlimitation, consider a scenario where a user's mobile phone is regularlyprovisions personalization data to the cloud service and subsequently isdisabled or lost. Utilizing the cloud service, a newly purchased phonecan be configured out of the box to be nearly identical to the previousphone with respect to contacts (e.g., address book), content (e.g.,music, video, pictures . . . ), settings (e.g., ring tones, wallpaper .. . ), and/or the like.

FIG. 8 is a flow chart diagram of a migration service method 800 inaccordance with an aspect of the claimed subject matter. At referencenumeral 810, personalization data is acquired from a device such asmobile phone, for example. The acquired data is persisted to at leastone data store at numeral 820. In one instance, such data can bepartitioned by identity or persona (e.g., work, personal . . . ) tofacilitate retrieval and provisioning of such information. At reference830, the acquired and/or persisted personalization data is provisionedto at least a second device. The act of provisioning can be automatic,semi-automatic, and/or responsive to a request for such data.Furthermore, the amount and type of data provisioned can be a functionof identity, device capabilities, and/or network connectivity, amongother things.

FIG. 9 depicts a method of device configuration 900 according to anaspect of the claimed subject matter. At reference numeral 910, a deviceacquires personalization data from a cloud service such as installedapplications, content (e.g., music, video, pictures . . . ), settings,and/or state. In one instance, the device can be cognitive in nature inthat it will sense available resources (e.g., near WiFi, availablelicensed band, unlicensed band . . . ) and modify behavior as a functionof user movement (moving toward an area with limited resources).Furthermore, the data acquired can be a function of identity, devicecapabilities, and/or network connectivity, among other things. At 920,this data is employed to configure a device. With respect to a mobilephone, applications (e.g., navigator, document viewer . . . ) andcontacts can be loaded, ring tones and background set and stateestablished, for example.

FIG. 10 is a flow chart diagram of a method of communication processingutilizing device migration 1000 in accordance with an aspect of theclaimed subject matter. At reference numeral 1010, a determination ismade as to whether a communication has been received such as a telephonecall. If not, the method 1000 continues to loop until a communication isindeed acquired. If a communication is received, then method 1000continues at 1020 where another determination is made concerning theavailability of a device to which the communication is directed. Forexample, a device can be unavailable due to a low battery or residing ina communication dead zone, among other things. If the device isavailable, the communication is transmitted to the device at reference1050. Alternatively, if the device is unavailable the method 1000continues at 1030 where a target device is identified. Among otherthings, this can be a result of an explicit designation, preference orrule and/or an automatic procedure, for instance via identification ofnearby devices. At reference numeral 1040, settings, state informationor the like are pushed to the target device to facilitate configurationthereof. The communication can then be transmitted to the configuredtarget device at numeral 1050.

Turning to FIG. 11, a multiple device migration method 1100 is depictedin accordance with an aspect of the claimed subject matter. At reference1110, a call or other communication is received on a primary device suchas a mobile phone. At numeral 1120, a determination is made pertainingto whether a secondary device is available. If no the method 1100 simplyterminates. If yes, call and all settings and/or personalization data ispushed or moved to the primary and/or secondary device. For example,portions of the communication such as speech and video can be split suchthat voice is transmitted across a primary mobile phone and video ispresented on a proximate television or computer monitor. Further, as auser moves about the video and settings can be migrated to the closestavailable video monitor.

As used herein, the terms “component,” “system” and the like areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution. For example, a component may be, but is not limited to being,a process running on a processor, a processor, an object, an instance,an executable, a thread of execution, a program, and/or a computer. Byway of illustration, both an application running on a computer and thecomputer can be a component. One or more components may reside within aprocess and/or thread of execution and a component may be localized onone computer and/or distributed between two or more computers.

A “cloud” or “cloud service” is intended to refer to a collection ofresources (e.g., hardware and/or software) provided and maintained by anoff-site party (e.g., third party), wherein the collection of resourcescan be accessed by an entity over a network (e.g., Internet, WAN . . .). The resources provide services including, without limitation, datastorage services and migration services as described above. In oneinstance, a cloud service can be embodied as a web, Internet, orapplication service but is not limited thereto.

The word “exemplary” or various forms thereof are used herein to meanserving as an example, instance, or illustration. Any aspect or designdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Furthermore,examples are provided solely for purposes of clarity and understandingand are not meant to limit or restrict the claimed subject matter orrelevant portions of this disclosure in any manner. It is to beappreciated that a myriad of additional or alternate examples of varyingscope could have been presented, but have been omitted for purposes ofbrevity.

As used herein, the term “inference” or “infer” refers generally to theprocess of reasoning about or inferring states of the system,environment, and/or user from a set of observations as captured viaevents and/or data. Inference can be employed to identify a specificcontext or action, or can generate a probability distribution overstates, for example. The inference can be probabilistic—that is, thecomputation of a probability distribution over states of interest basedon a consideration of data and events. Inference can also refer totechniques employed for composing higher-level events from a set ofevents and/or data. Such inference results in the construction of newevents or actions from a set of observed events and/or stored eventdata, whether or not the events are correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources. Various classification schemes and/or systems(e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, data fusion engines . . . ) canbe employed in connection with performing automatic and/or inferredaction in connection with the subject innovation.

Furthermore, all or portions of the subject innovation may beimplemented as a method, apparatus or article of manufacture usingstandard programming and/or engineering techniques to produce software,firmware, hardware, or any combination thereof to control a computer toimplement the disclosed innovation. The term “article of manufacture” asused herein is intended to encompass a computer program accessible fromany computer-readable device or media. For example, computer readablemedia can include but are not limited to magnetic storage devices (e.g.,hard disk, floppy disk, magnetic strips . . . ), optical disks (e.g.,compact disk (CD), digital versatile disk (DVD) . . . ), smart cards,and flash memory devices (e.g., card, stick, key drive . . . ).Additionally it should be appreciated that a carrier wave can beemployed to carry computer-readable electronic data such as those usedin transmitting and receiving electronic mail or in accessing a networksuch as the Internet or a local area network (LAN). Of course, thoseskilled in the art will recognize many modifications may be made to thisconfiguration without departing from the scope or spirit of the claimedsubject matter.

In order to provide a context for the various aspects of the disclosedsubject matter, FIGS. 12 and 13 as well as the following discussion areintended to provide a brief, general description of a suitableenvironment in which the various aspects of the disclosed subject mattermay be implemented. While the subject matter has been described above inthe general context of computer-executable instructions of a programthat runs on one or more computers, those skilled in the art willrecognize that the subject innovation also may be implemented incombination with other program modules. Generally, program modulesinclude routines, programs, components, data structures, etc. thatperform particular tasks and/or implement particular abstract datatypes. Moreover, those skilled in the art will appreciate that thesystems/methods may be practiced with other computer systemconfigurations, including single-processor, multiprocessor or multi-coreprocessor computer systems, mini-computing devices, mainframe computers,as well as personal computers, hand-held computing devices (e.g.,personal digital assistant (PDA), phone, watch . . . ),microprocessor-based or programmable consumer or industrial electronics,and the like. The illustrated aspects may also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network.However, some, if not all aspects of the claimed subject matter can bepracticed on stand-alone computers. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

With reference to FIG. 12, an exemplary environment 1210 forimplementing various aspects disclosed herein includes a computer 1212(e.g., desktop, laptop, server, hand held, programmable consumer orindustrial electronics . . . ). The computer 1212 includes a processingunit 1214, a system memory 1216, and a system bus 1218. The system bus1218 couples system components including, but not limited to, the systemmemory 1216 to the processing unit 1214. The processing unit 1214 can beany of various available microprocessors. It is to be appreciated thatdual microprocessors, multi-core and other multiprocessor architecturescan be employed as the processing unit 1214.

The system memory 1216 includes volatile and nonvolatile memory. Thebasic input/output system (BIOS), containing the basic routines totransfer information between elements within the computer 1212, such asduring start-up, is stored in nonvolatile memory. By way ofillustration, and not limitation, nonvolatile memory can include readonly memory (ROM). Volatile memory includes random access memory (RAM),which can act as external cache memory to facilitate processing.

Computer 1212 also includes removable/non-removable,volatile/non-volatile computer storage media. FIG. 12 illustrates, forexample, mass storage 1224. Mass storage 1224 includes, but is notlimited to, devices like a magnetic or optical disk drive, floppy diskdrive, flash memory, or memory stick. In addition, mass storage 1224 caninclude storage media separately or in combination with other storagemedia.

FIG. 12 provides software application(s) 1228 that act as anintermediary between users and/or other computers and the basic computerresources described in suitable operating environment 1210. Suchsoftware application(s) 1228 include one or both of system andapplication software. System software can include an operating system,which can be stored on mass storage 1224, that acts to control andallocate resources of the computer system 1212. Application softwaretakes advantage of the management of resources by system softwarethrough program modules and data stored on either or both of systemmemory 1216 and mass storage 1224.

The computer 1212 also includes one or more interface components 1226that are communicatively coupled to the bus 1218 and facilitateinteraction with the computer 1212. By way of example, the interfacecomponent 1226 can be a port (e.g., serial, parallel, PCMCIA, USB,FireWire . . . ) or an interface card (e.g., sound, video, network . . .) or the like. The interface component 1226 can receive input andprovide output (wired or wirelessly). For instance, input can bereceived from devices including but not limited to, a pointing devicesuch as a mouse, trackball, stylus, touch pad, keyboard, microphone,joystick, game pad, satellite dish, scanner, camera, other computer andthe like. Output can also be supplied by the computer 1212 to outputdevice(s) via interface component 1226. Output devices can includedisplays (e.g., CRT, LCD, plasma . . . ), speakers, printers and othercomputers, among other things.

FIG. 13 is a schematic block diagram of a sample-computing environment1300 with which the subject innovation can interact. The system 1300includes one or more client(s) 1310. The client(s) 1310 can be hardwareand/or software (e.g., threads, processes, computing devices). Thesystem 1300 also includes one or more server(s) 1330. Thus, system 1300can correspond to a two-tier client server model or a multi-tier model(e.g., client, middle tier server, data server), amongst other models.The server(s) 1330 can also be hardware and/or software (e.g., threads,processes, computing devices). The servers 1330 can house threads toperform transformations by employing the aspects of the subjectinnovation, for example. One possible communication between a client1310 and a server 1330 may be in the form of a data packet transmittedbetween two or more computer processes.

The system 1300 includes a communication framework 1350 that can beemployed to facilitate communications between the client(s) 1310 and theserver(s) 1330. The client(s) 1310 are operatively connected to one ormore client data store(s) 1360 that can be employed to store informationlocal to the client(s) 1310. Similarly, the server(s) 1330 areoperatively connected to one or more server data store(s) 1340 that canbe employed to store information local to the servers 1330.

Client/server interactions can be utilized with respect to enablingmigration as described herein. For example, the cloud migration servicecan be executed by one or more server(s) with respect to clients 1310including mobile communication devices among others across thecommunication framework 1350. More specifically, personalization datasuch as settings and/or state information can be transmitted to and fromclient data store(s) 1360 and server data store(s) 1340 to effectmigration.

What has been described above includes examples of aspects of theclaimed subject matter. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the claimed subject matter, but one of ordinary skill in theart may recognize that many further combinations and permutations of thedisclosed subject matter are possible. Accordingly, the disclosedsubject matter is intended to embrace all such alterations,modifications and variations that fall within the spirit and scope ofthe appended claims. Furthermore, to the extent that the terms“includes,” “contains,” “has,” “having” or variations in form thereofare used in either the detailed description or the claims, such termsare intended to be inclusive in a manner similar to the term“comprising” as “comprising” is interpreted when employed as atransitional word in a claim.

What is claimed is:
 1. A computing device configured to facilitateprovisioning of a remote device, the computing device comprising: adevice detection component configured to identify the remote device; areceiving component configured to receive: personalizations for thecomputing device, the personalizations being associated with a user, anda request to provision the remote device; a processor configured todetermine a subset of the personalizations based on differences betweenfunctionality of the computing device and functionality of the remotedevice; and a transmission component configured to transmit the subsetof the personalizations to the remote device to cause the remote deviceto be provisioned.
 2. The computing device of claim 1, wherein thedevice detection component is further configured to identify the remotedevice using near field communication protocols.
 3. The computing deviceof claim 1, wherein the personalizations are provisioned for the userbased on identity.
 4. The computing device of claim 1, wherein thedevice detection component is further configured to identify the remotedevice as a function of location.
 5. The computing device of claim 1,further comprising a translation component configured to translate thepersonalizations from a first proprietary form to a second proprietaryform.
 6. The computing device of claim 1, further comprising anormalization component configured to transform the personalizations toa standard form.
 7. The computing device of claim 1, further comprisingan identity component configured to partition personalizations as afunction of identities associated with the user.
 8. A method forfacilitating device provisioning comprising: identifying, by a firstmobile communications device, a second mobile communications device;storing, by the first mobile communications device, personalizationsassociated with a user; receiving, by the first mobile communicationsdevice, a request to provision the second mobile communications device;determining, by the first mobile communications device, a subset of thepersonalizations for a user based on differences between functionalityof the first and second mobile communications devices; and transmittingthe subset of the personalizations to the second mobile communicationsdevice.
 9. The method of claim 8, wherein the identifying furthercomprises identifying the second mobile communications device using nearfield communication technologies.
 10. The method of claim 8, wherein thepersonalizations associated with the user are provisioned based on useridentity.
 11. The method of claim 8, wherein the identifying furthercomprises identifying the second mobile communications device based onlocation.
 12. The method of claim 8, further comprising translating thepersonalizations from a first proprietary form to a second proprietaryform.
 13. The method of claim 8, further comprising transforming thepersonalizations to a standard form.
 14. The method of claim 8, furthercomprising partitioning personalizations based on multiple identitiesand/or personas associated with the user.
 15. A storage device havingstored thereon computer-executable instructions for performingoperations comprising: receiving personalizations for a first mobilecommunications device, the personalizations being associated with auser; identifying a second mobile communications device; receiving arequest to provision the second mobile communications device; responsiveto the request, determining a subset of the personalizations based ondifferences between functionality of the first and second mobilecommunications devices; and sending the subset of the personalizationsto cause the second mobile communications device to be provisioned. 16.The storage device of claim 15, wherein the subset of thepersonalizations is determined based on the second mobile communicationsdevice having phone functionality.
 17. The storage device of claim 16,wherein the subset of the personalizations comprises at least one ofcontacts, ring tones, settings, preferences, or rules.
 18. The storagedevice of claim 15, wherein the operations further comprise translatingthe personalizations from a first proprietary form to a second.
 19. Thestorage device of claim 15, wherein the operations further comprisetransforming the personalizations to a standard form.
 20. The storagedevice of claim 15, wherein the operations further comprise identifyingthe second mobile communications device using near field communicationprotocols.